Most of the remaining problems with the user interface (U/I) are tied to my use in Mac F2C of Codewarrior’s SIOUX console library. These remaining problems will be fixed in future releases when I implement my own console window (or CodeWarrior improves theirs). These, and other U/I problems are described below.
There is one code generation problem in version 1.3.2, but it has an easy work around.
Known User Interface Problems
• The cursor flickers between an I-beam and an arrow while over an editable text field in a dialog box. This is due to an unwanted interaction with the SIOUX console window. I do not know when this will be fixed.
• The Undo command does not work. It is not implemented at this time.
• The Close command does not work. It is not implemented at this time. There is no way to close the translation status window in this version of Mac F2C.
• The translation status window is always saved as a CodeWarrior text file, regardless of the creator code specified in the Mac F2C Preferences dialog.
Known Code Generation Problems
• There is one confirmed bug that causes the PPC version of Mac F2C to crash when translating a particular piece of FORTRAN code. As far as I know, it only happens with only one specific piece of FORTRAN code submitted by a Mac F2C user. It is 100% reproducible, but I have not been able to isolate the problem (probably because I don’t have regular access to a PPC Macintosh). The work-around is to use the 68K version of Mac F2C, either by running it on a 68K Macintosh, or deleting the ‘cnfg’ resource from the (fat) Mac F2C application.
